chore: make toy tutorials robust against pre-existing IDs#2269
Open
nhoening wants to merge 3 commits into
Open
chore: make toy tutorials robust against pre-existing IDs#2269nhoening wants to merge 3 commits into
nhoening wants to merge 3 commits into
Conversation
… IDs, also less work for users Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
4 tasks
Flix6x
approved these changes
Jul 8, 2026
Flix6x
left a comment
Member
There was a problem hiding this comment.
Did you successfully run the QA workflow against this branch?
| }, | ||
| ] | ||
|
|
||
| # the site gets a similar dashboard (TODO: after #1801, add also capacity constraint) |
Member
There was a problem hiding this comment.
Could be a small bonus for this PR?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
IDs of assets or sensors might already exist. I came across this in #2268.
This makes our tutorials inherently unstable in the docs and our CI scripts.
And users have to manually copy IDs if they ever run tutorials from a non-empty starting position.
documentation/changelog.rstLook & Feel
Not many changes in the tutorial flow, using var names instead of hard-coded IDs.
How to test
Run tutorials (also part of our CI)